Fix torture tests setup #17
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR, implicitly, the
TortureTestsrelied on theBundlingTeststo be run earlier, because:@BeforeAllof theBundlingTestsconfigured Awaitility in a way that was also needed by theTortureTests(setting the default timeout long enough).TortureTestsdidn't have its own@BeforeAllto do this configuration.In earlier CI runs, coincidentally, the
BundlingTestswere indeed run before theTortureTests, so it all went fine. In recent CI runs, though, the order was the other way around, causing them to inexplicably fail.This PR adds a
@BeforeAllto theTortureTeststo make the CI runs predicable again. This PR also fixes a few warnings to improve the code quality of the tests.